Scenario #5006: Subscribe Another Person to Existing Mailinglist As Normal User

Properties

Required

• Mailinglist: first-gmbh-internal from 5005: Create New Mailinglist As Global Admin

Given

name	value
partnerPersonTradeName	First GmbH
subscriberFamilyName	Miller
subscriberGivenName	Frida
subscriberEMailAddress	frida.miller@example.org
mailingList	first-gmbh-internal

Person: First GmbH

HTTP GET "/api/hs/office/persons?name=First+GmbH" \
  -H "Authorization: Bearer $HSADMINNG_JWT_BEARER" \
  `# {` \
  `#   "sub" : "uuid<tst-person_firbysusan>"` \
  `# }`
=> status: 200 OK 
[ {
  "uuid" : "20843a67-f6d5-415a-af9d-71319bb7df43", // Person: First GmbH
  "personType" : "LEGAL_PERSON",
  "tradeName" : "First GmbH",
  "salutation" : null,
  "title" : null,
  "givenName" : null,
  "familyName" : null
} ]

In production, data this query could result in multiple outputs. In that case, you have to find out which is the right one.

Subscribe Frida Miller to first-gmbh-internal

HTTP POST "/api/hs/office/relations" \
  -H "Authorization: Bearer $HSADMINNG_JWT_BEARER" \
  `# {` \
  `#   "sub" : "uuid<tst-person_firbysusan>"` \
  `# }` \
  <<EOF
{
  "type" : "SUBSCRIBER",
  "mark" : "first-gmbh-internal",
  "anchor.uuid" : "20843a67-f6d5-415a-af9d-71319bb7df43", // Person: First GmbH
  "holder" : {
    "personType" : "NATURAL_PERSON",
    "familyName" : "Miller",
    "givenName" : "Frida"
  },
  "contact" : {
    "caption" : "Frida Miller",
    "emailAddresses" : {
      "main" : "frida.miller@example.org"
    }
  }
}
EOF
=> status: 201 CREATED e79e589e-f61a-4225-bbb7-abba1c5bf844

---

generated on 2026-08-10 04:42:28 for branch HEAD